Skip to content

chore(main): release 0.54.0 - #427

Merged
sunib merged 1 commit into
mainfrom
release-please--branches--main--components--gitops-reverser
Oct 26, 2026
Merged

sunib merged 1 commit into
mainfrom
release-please--branches--main--components--gitops-reverser

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.54.0 (2026-10-26)

⚠ BREAKING CHANGES

  • metrics: every branch-worker series carries gitbranch_namespace and gitbranch_name and drops branch; provider_namespace and provider_name stay. git_branch_targets maps a GitTarget to its GitBranch only. appliers_held, stale_snapshots_total and claimed_resource_reconciled_total are renamed apply_appliers_held, apply_stale_snapshots_total and apply_claimed_resource_reconciled_total. git_commit_failures_total and git_writes_dropped_total drop kind, git_commit_windows_total has no close_reason="atomic_before_apply", git_fetches_total has no reason="bootstrap", and attribution_resolution_wait_seconds carries only tier and event_kind. See docs/UPGRADING.md, "Metrics: the branch worker's series name their GitBranch, and three apply series are renamed".
  • api: who may use a GitProvider, a GitBranch or a KubeProvider is a list of grants on that object: GitProvider.spec.allowedGitBranches (replaces spec.allowedBranches), GitBranch.spec.allowedGitTargets, and KubeProvider.spec.allowedGitTargets and spec.allowedApplierClaims (replace ClusterProvider spec.accessFrom and spec.allowCrossNamespace). Each grant names its consumers in a required consumerNamespaces block (from: Same, Names, Selector or All). On a GitBranch or a KubeProvider an omitted list admits the object's own namespace; a GitProvider's list has no default, so omitted it admits no GitBranch. See docs/UPGRADING.md, "Grants say who may use a provider or a branch".
  • applier: rename FluxTrigger/ArgoCDTrigger to FluxClaim/ArgoCDClaim (#438)
  • applier: hold an Argo CD Application's automated sync off, as a suspend (#437)
  • one GitReceiver for many repositories (#432)
  • replace ClusterProvider with a namespaced KubeProvider (#430)
  • hold a repository branch with a GitBranch (#429)
  • a repository branch has one branch worker, keyed by the repository's URL and the branch, so an https and an SSH spelling of one repository are one branch. The GitBranch holding the branch decides which GitProvider's credential pushes it, and a GitProvider in another namespace is shared through the grants on it (spec.allowedGitBranches) and the GitBranch's spec.gitProviderRef.namespace, never copied. See docs/UPGRADING.md, "GitBranch holds a repository branch" and "Grants say who may use a provider or a branch".
  • an apply no longer waits for a quiet branch: the branch worker publishes what is pending, then applies. FluxClaim, which replaces FluxTrigger, has no spec.quietPeriod and no status.source.prefetch, so leave spec.quietPeriod out when you create each FluxClaim from a 0.53.0 FluxTrigger. See docs/UPGRADING.md, "An applier claim applies once the branch is published, and an ArgoCDClaim holds automated sync off".

Features

  • answer the gitops-api team's open asks (#445) (be991b8)
  • api: an omitted GitBranch or KubeProvider grant list admits the object's own namespace (#442) (0579999)
  • api: explicit access grants between providers, branches and their users (#441) (1c4fade)
  • applier: hold an Argo CD Application's automated sync off, as a suspend (#437) (dec7056)
  • hold a repository branch with a GitBranch (#429) (17c0c96)
  • metrics: label branch-worker metrics by GitBranch, act on the metrics review, and reconcile the docs (#450) (8436844)
  • one branch worker per repository branch, whatever GitProvider names it (#428) (c49803f)
  • one GitReceiver for many repositories (#432) (6ae6272)
  • recognize the applier's own writes, and flush before applying (#425) (2d98259)
  • replace ClusterProvider with a namespaced KubeProvider (#430) (5d7d5f8)

Bug Fixes

  • attribution: credit a removal by what caused it, never by the watch's selector (#431) (a52caca)
  • controller: publish a refreshed status.remote when the floor lifts, and time the bi-directional loop (#424) (3f00e09)
  • git: hold a live edit made while a GitTarget's render fidelity is pending, instead of dropping it (#443) (1bc9790)

Documentation

  • api: CRD description proposal, its review, and its implementation (#448) (9ca1178)
  • close the release gate in the TODO (#444) (f4ae056)

Code Refactoring

  • applier: rename FluxTrigger/ArgoCDTrigger to FluxClaim/ArgoCDClaim (#438) (efc0203)

This PR was generated with Release Please. See documentation.

@coderabbitai

coderabbitai Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 14053121-9cc0-453d-bafd-241004ec08ed

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--gitops-reverser branch 5 times, most recently from 774815f to 949bcaa Compare October 23, 2026 15:06
sunib
sunib previously approved these changes Oct 23, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--gitops-reverser branch 2 times, most recently from 1d717ac to 8736058 Compare October 24, 2026 15:12
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--gitops-reverser branch 3 times, most recently from f801427 to b28308b Compare October 26, 2026 09:58
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--gitops-reverser branch from b28308b to b148f3d Compare October 26, 2026 10:07
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--gitops-reverser branch from b148f3d to e9ea0d5 Compare October 26, 2026 10:09
@sunib
sunib merged commit bbbe91f into main Oct 26, 2026
4 checks passed
@sunib
sunib deleted the release-please--branches--main--components--gitops-reverser branch October 26, 2026 10:15
@codecov

codecov Bot commented Oct 26, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant